First draft of ipfs: URI spec, see #138, replaces PR #139 #222
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lidel
reviewed
Oct 23, 2019
There was a problem hiding this comment.
I just realized this spec comes from 2016 and is bit outdated.
Needs at least updates suggested in #139 (review)
Not sure if we want separate spec document for URLs.
My plan was to incorporate content from https://docs.ipfs.io/guides/guides/addressing/ into sections of https://github.com/ipfs/specs/blob/master/DWEB_ADDRESSING.md
@pawal do you want to change this PR to add a section about URIs to DWEB_ADDRESSING instead?
We could also park this PR until changes described in #152 (comment) land first.
|
I am closing in favour to #152 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.